V1.1 I forgot to comment the code. I felt like that would be a useful thing to do so that people understand how this works. Also, I changed the massive if chain in the tick() function to an elseif chain which should slightly improve performance, though optimization has never been my strong suit, so if anyone wants to try to fix my spaghetti code, be my guest.
This is my first thing that I made outside of simple experimentation with the engine! I hope you all like it! Most things have interactions with most other things, so just play around and see what you can do!
0 comments
what have I done
Thank you to Dylan Bennett for the tutorial!
This is my first game, I hope you enjoy it
This is a small game about a small dragon kid that jumps around collecting gold and video game treasures.
This was my first PICO-8 project (and "finished", published game).
How to play:
You control a small dragon kid. You can jump on slimes, and bounce off slime balloons. You can jump up — or off — walls.
If a slime knocks you out, or if you land on spikes, you will lose 5 gold. Gold is worth 1, and video game treasures/large gold bricks are worth 10. Try to collect as much gold and treasure as you can!
Special thanks:
Though "complete", it isn't very long, and ends abruptly.
My intention was to just mess around with PICO-8, but after watching Krystman (Lazy Devs) talk about the importance of finishing your first game (in this video), I felt compelled to get it in a finished state and put it out, before moving on to start something new.
I hope you enjoy the game, and pardon the bugs, code, art, and lack of background music! x)
I found that, when entering the editors, the map resets itself and, furthermore, resets the map for the game being currently played as well.
An example of this bug (using Super Mario Remix):
@zep can you please fix this or make this a setting or something? (I would prefer it being a setting available using config)
Hi there.
I wonder if this is a bug.
I'm messing around with pico 8 trying to make a shmup and after woking for a while in the shooting mechanics of enemies and player I decided to start with the level design.
The thing is I drew some enemies on the map just to try things out and now my spritesheet is showing some strange artifacts as if it had become corrupted.
Is this normal?
Thanks, have a good day.
Map
Spritesheet
The Pacifist is a shooter where you don't shoot, you move. It builds upon Geometry Wars' Pacifism Mode.
How to play
The goal is to pass through gates when there are enemies in the circle around it. Each enemy killed that way raises the multiplier and gives points.
There are three lives, represented by the condition of the ship. The darker the ship, the less lives you have left.
There are two base powers:
- Time Freeze: Use the Z/0 button to freeze time for 1.5 seconds. It uses a portion of the power bar.
- Shield: Use the X button to use a shield, repelling enemies that are close to you.
Powerups pop up now and then to help you.
Known bugs
- When dying after the third life, enemies spawn immediately but they shouldn't.
Version History
Version 0.8.4
- Bugfix
Version 0.8.3
- Fixed a bug that made it possible to have virtually infinite shield
- Changed the way power-ups are picked. You have a choice of two power ups and have 10 seconds to decide which one to pick. At the beginning, you don't get two power-ups like you used to, but the time between power-up spawns has been reduced.
Version 0.8.2
- Replaced the Dimensional Shift with a time freeze power on the Z button.
- Added a power-up to level up the time freeze (making it use less energy)
Version 0.8.1
- New enemy type spawns later
Version 0.8
- Changed the color palette so enemies would be even more clear
- Added a new type of enemy
- Adjusted the difficulty
Version 0.7.4
- small bugfix relating to Performance Mode
Version 0.7.3
- Fixed some powerups that were not spawning.
- Fixed the shield radius.
- Added a power-up to level up the shield, decreasing its energy usage and increasing its range slightly.
Version 0.7.2
- Added a shield on the x button that shares its power bar with the Dimensional Shift. I think it's fun to use, but renders the Shift almost moot. I'll have to rebalance those two powers in a future version.
- Made the enemies go in slighty off directions the farther they are from the player. It's subtle but it prevents enemies from all doing the exact same thing.
Version 0.7.1
- Hotfix
Version 0.7
- Added audio and visual feedback when gates are spawning.
- Pink dot's countdown now affects the background grid.
- Added a true difficulty curve (instead of hadcoded spawns) For now it's not a curve, it's linear, but I'll try to adjust it to make it fair to new players and fun for veterans.
- Fixed the diagonal player angles which made it possible for enemies to spawn in the trajectory of the player.
- Small ajustments to powerups.
Version 0.6.2.2
- Fixed a memory leak caused by some particles not removing themselves.
- The physics-based grid now updates at 30fps instead of 60. It makes it run almost flawlessly on RG351 devices.
Version 0.6.2.1
- Added a menu option to disable the physics-based background grid for slower devices.
Version 0.6.2
- Re-arranged enemy physics to make them more bouncy. As a result, it can be a bit easier, but I think it's for the better.
- Added a physics-based background grid to make things more dynamic. The physics engine was made by aatish (https://www.lexaloffle.com/bbs/?pid=84525)
- Fixed the GateUp powerup. Now, you are limited to 3 stacks of this powerup.
Version 0.6.1
- Made the pink and orange enemies more aggressive
- The Slow Pink powerup was removed
- Added visual and audio feedback when catching a powerup
Version 0.6
- Expanded the play field to 192x192 instead of 128x128. It drastically changes the balance of the game so I'm still not sure if that's what I want.
- To counter-balance the first point, I changed the spawn rate of enemies. The pink one is less lethal so I'll try to balance it in the future.
- Added 5 types of powerups that spawn randomly every 45 seconds
- Extended the song
- Cleaned up the UI
- Removed the fake background scroll because it became very weird with the real scrolling field.
Version 0.5.2
- Fixed the score limit. Now the theoretical limit is 999,999,999 points, although the display will probably be broken at that point.
- Fixed a very minor sound problem when killing enemies
- Small refactoring
Version 0.5.1
- Nothing added, simply a refactoring because the code was getting messy and hard to work with.
Version 0.5
- Initial version here. To learn to play, look for the "How to play" section below.
What's next?
- Balance out the powers
- Add more power-ups
- Add debuffs (maybe)
- Adjust difficulty
- Adjust, adjust and adjust to optimize the fun and make it rewarding
Enjoy!
Little platformer test I made by a combination of different tutorials.
Update #2: Now with animation and changed jump button to X
Update #1: Now with coyote time
previous version(s)
Controls:
left, right = run
up = jump
Can wallslide when falling and pressing into a wall
Can wall jump when pressing up next to a wall
Can slide a bit when running then run in the opposite direction. Doing so on less frictious floors results in cooler effect.
Enjoy.
-Gravitoid
.jpeg)
A modification of the Celeste SOBcart!
New features:
Save best times using cartdata, so times are saved even after closing the cart
Toggle spawning times being counted in your time w
Delete current level (or all levels on Summit) best time from pause menu
Hello all.
I'm brand new to all things Pico 8, having dabbled with programming since the 80s.
I'm having LOTS of problems though.
I added particles to my platform player.
I saw a tutorial about adding objects and function within them, so I tried to change my particle system.
It broke. The error says: Unclosed { but I can't find where I've gone wrong.
I apologise if this isn't how to post code on this.
Can someone help out, please. (This is trimmed down in the hope I don't over stay my welcome!)
function _init()
....
particle={}
end
function add_new_particle(x,y,die,dx,dy,grav,grow,shrink,r,c_table)
add(particle,{
x=x,
y=y,
t=0,
die=die,
dx=dx,
dy=dy,
grav=grav,
grow=grow,
shrink=shrink,
r=r,
c=0,
c_table=c_table
draw=function(self)
if self.r<=1 then
pset(self.x,self.y,self.c)
else
circfill(self.x,self.y,self.r,self.c)
end
end,
update=function(self)
self.x+=self.dx
self.y+=self.dy
if self.grav then self.dy+=.5 end
if self.grow then self.r+=.1 end
if self.shrink then self.r-=.2 end
self.t+=1
if self.t>self.die then del(particle,self) end
if self.t/self.die < 1/#self.c_table then
self.c=self.c_table[1]
elseif self.t/self.die < 2/#self.c_table then
self.c=self.c_table[2]
elseif self.t/self.die < 3/#self.c_table then
self.c=self.c_table[3]
else
self.c=self.c_table[4]
end
end
})
end
function dust()
add_new_particle(plyr.x,plyr.y,10+rnd(7),rnd(2)-1,rnd(.3)-.4,false,true,true,3,{4,4,5,5})
end
function runs()
add_new_particle(plyr.x,plyr.y,10+rnd(7),rnd(2)-1,rnd(1)-0.5,false,false,true,2,{4,4,5,5})
endWhen the player lands on a platform, I have this: But it doesn't get this far.
dust()
sfx(0)
I haven't even figured what to put in the _draw function yet.
I hope this isn't too much to see what I'm trying to do and makes a bit of sense to someone.
Thanks for your time.
Peej
Hello. I recently Bought Voxatron and I entered by the first start the splore. Now when I try to make a new Project I always land in Arena Shooter game Project. and also how can I go out from the splore and visit the start screen again? Could someone Help me with that? Thanks :>
This is a little top-down legend of zelda like game. I hope you enjoy it!
(the music transition going in and out of the forest is a bit janky, but I couldn't figure out a better way to do it.)
This is a work in progress puzzle game, currently with 6 levels. Z to pick up / drop boxes, or jump. X restarts the level. You must put all of the boxes onto the button to unlock the door.
Unsafe at Home: A 64x64 baseball bullet hell time wasting experience!
In the distant future, Blaseball is the only remaining sport, as foretold by prophecy. One day, two friends run across an ancient document: the official Major League Baseball rulebook. However, it is badly damaged and the two are left to interpret the rules for themselves. Here is what these two friends from the future think baseball used to be.
- One player, the pitcher, attempts to hit the other player, the hitter, with baseballs. The book clearly says hitter, not hittee, which would make more sense, but these were ancient humans, so . . .
- The hitter attempts to circle the bases counterclockwise as many times as he can without getting hit. Each time he does this, he scores a run. He must stay in the baseline at all times. He can circle the bases clockwise, but will not score runs in that direction, and in fact must recircle ALL the bases he circled clockwise in the correct direction before he is awarded a run for crossing "home", which is what people called fourth base in those days.
- When the hitter scores 5 runs without having a bat, he gets a bat. The bat is used to hit home runs (maybe tihs is why he's called "hitter" and not "hittee"? The text is ambiguous). A home run clears all the balls from the field, but is obviously not worth any runs - that would be nonsense.
- If the hitter chooses NOT to use the bat, he gets an extra run for every run he accumulates after getting the bat until he chooses to use the bat.
- When the pitcher hits the hitter, that is called an inning (because the ball runs INto the hitter). The baseballs they found with the rulebook are all very old and immediately disintegrate when they run into the hitter. The game ends after 9 innings.
- The pitcher throws a ball at the hitter once at the start of the game, once for every run the hitter scores, once after a home run, and once when he scores an inning. Every 5 runs the hitter scores, the pitcher starts throwing a little harder.
GOAL
Score as many runs as you can before the end of the 9th inning. My personal best is 21, I'd love to see how you do!
CONTROLS
- Any key to start the game from the title screen.
- Up arrow to run counterclockwise, down arrow to run clockwise. You only score runs running the bases in the correct (counterclockwise) direction, but running backwards is key to avoid getting hit sometimes!
- X or Z to hit a home run when you have the bat!
- X or Z to restart when the game ends.
CREDITS
I'm responsible for all the code, music arrangement & mediocre pixel art, such as it is. The concept came to me when I was watching an actual baseball game and saw the baserunner get hit during a rundown. It's 64x64 because it's harder and more chaotic that way :).
The music for "Take Me Out to the Ball Game" was composed in 1908 by Albert Von Tilzer, 20 years before he ever saw a baseball game. I think I took a few liberties with some notes here and there, but it's mostly faithful to the original.
Worm Simulator!
This isn't much of a game, just the first thing I made to get acquainted with PICO-8! You play as a worm that can dig around in the dirt, moved by the arrow keys. Might go back to this someday to turn it into an actual fleshed out game :-)
Pico's Big Adventure release!
Finally my first pico game reached a sort of completed stage: start menu, three levels, minimal sounds, gorgeous (?) graphics... I'm pretty happy with it, and I hope you'll have fun playing!
Controls:
- jump with X,
- launch yoyo with C
- launch stones with C plus down arrow
- pickup shrubs with down arrow
The original, Terry's big adventure, had some nice ideas I managed to port here, and was somewhat original - even if I can't be sure it wasn't ripping off something, apart from being a mario clone, or at least sailing on mario popularity- due to an improbable weapon and some bizzarre enemies.
I tried to keep the code organized and readable, but lost focus here and there. If that doesn't hold you back, feel free to reuse the code. It's nothing original, but the animation system let you create a variety of behaviours, all you have to do is define some general characteristics and add sequences of sprites along with optional movement modifiers. Maps let you place enemies with the "id" sprite, and modifiers for starting behaviour and drops can be placed in an adjacent tile.
Running the cart will copy to clipboard the encoded level, even if the core game takes around 6000 tokens so it's hard to fit more than three or four levels. I want to take some time and optimize the core code, along with the encoding and storing of levels, as this kind of game can benefit from more levels.
